home *** CD-ROM | disk | FTP | other *** search
/ InfoMagic Internet Tools 1995 April / Internet Tools.iso / dos_win / winsock / maillist / 94-02.Z / 94-02 / text0005.txt < prev    next >
Encoding:
Text File  |  1994-02-28  |  6.7 KB  |  171 lines

  1.  
  2.  
  3. I need to write my own telnet client -- although I've written serial
  4. communications, I've never done telnet.  I'll be using Winsock and
  5. Novell's Lan Workgroup TCP/IP stack.
  6.  
  7. What I need are pointers, book references, and, most importantly, the
  8. telnet API specification.
  9.  
  10. If you have any suggestions, please reply by email to the address below.
  11. TIA!
  12.  
  13. PS: I realize that there are about a million versions of telnet out
  14. there; unfortunately, the circumstances require me to write my own
  15. customized version!
  16.  
  17. -- 
  18.  Nathan Silva                     | "Ignorance or apathy, which way?
  19.  Clark County School Employees CU |  We don't know and we don't care,
  20.  nathans@lri.rain.com             |  they say." -- Steve Taylor, "Squint"
  21. From news@bigblue.oit.unc.edu Tue Feb  1 06:06:30 1994
  22. Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.06) with SMTP
  23.           id AA29475; Tue, 1 Feb 1994 06:06:30 -0500
  24. Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
  25.           id AA26823; Tue, 1 Feb 1994 06:04:41 -0500
  26. Received: from GATEWAY by bigblue with netnews
  27.     for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
  28. To: winsock@sunsite.unc.edu
  29. Date: Tue, 1 Feb 1994 13:46:17
  30. From: ace@ics.forth.gr (Andreas C. Enotiadis)
  31. Message-Id: <ace.20.000DC5E0@ics.forth.gr>
  32. Organization: InterNetwork Ltd
  33. Sender: ses
  34. References: <1994Jan28.153923.9404@wvnvms.wvnet.edu>
  35. Subject: Re: NFS for WinSock
  36.  
  37. In article <1994Jan28.153923.9404@wvnvms.wvnet.edu> os361323@wvnvms.wvnet.edu writes:
  38. >Path: news.forth.gr!EU.net!howland.reston.ans.net!europa.eng.gtefsd.com!darwin.sura.net!wvnvms.wvnet.edu!os361323
  39. >From: os361323@wvnvms.wvnet.edu
  40. >Newsgroups: alt.winsock
  41. >Subject: NFS for WinSock
  42. >Message-ID: <1994Jan28.153923.9404@wvnvms.wvnet.edu>
  43. >Date: 28 Jan 94 15:39:22 -0500
  44. >Organization: West Virginia Network for Educational Telecomputing
  45. >Lines: 4
  46.  
  47.  
  48. >Does anyone know if there is such a thing as a shareeware/public domain
  49. >NFS package that is WinSock compliant.  If so, where can you get such
  50. >software.
  51.  
  52. As far as I know none (which is why I'm working on one but it looks like it 
  53. will take me a looong time at the rate my time availability decreases)
  54. Regards
  55. Andreas
  56.  
  57. --------------------------------------------------------------------------
  58. Andreas C. Enotiadis
  59. Internetwork Ltd
  60. "Just screwing around - for a living"
  61. ace@ics.forth.gr
  62. ace@iesl.forth.gr
  63. ace@praxis.forth.gr
  64. Snail-Mail : 1 Louki Akrita Str, 15237 Athens, Greece
  65. --------------------------------------------------------------------------
  66. From news@bigblue.oit.unc.edu Mon Jan 31 23:07:22 1994
  67. Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.06) with SMTP
  68.           id AA03563; Tue, 1 Feb 1994 07:36:30 -0500
  69. Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
  70.           id AA26765; Tue, 1 Feb 1994 07:33:16 -0500
  71. Received: from GATEWAY by bigblue with netnews
  72.     for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
  73. To: winsock@sunsite.unc.edu
  74. Date: Mon, 31 Jan 1994 23:07:22 GMT
  75. From: lsmith@symantec.com (Lindsey Smith)
  76. Message-Id: <lsmith.116.760057642@symantec.com>
  77. Organization: Symantec Corp.
  78. Sender: ses
  79. References: <blackout!rg61s62.1.00022716@xmission.com>
  80. Subject: Re: FSP
  81.  
  82. In article <blackout!rg61s62.1.00022716@xmission.com> blackout!rg61s62@xmission.com (Cardo) writes:
  83. >
  84. >      Does anyone know of another FSP client for Windows other than 
  85. >winfsp12.zip?  I want one that allows you to upload as well as download.  Any 
  86. >help would be greatly appreciated.
  87. >
  88. >Cardo
  89.  
  90. Have you tried the DOS FSP client? It implements all of the FSP 2.7.1 
  91. commands. You can FTP it from ftp.germany.eu.net (/pub/network/inet/fsp/
  92. pcfsp105.zip).
  93.  
  94. -----------------------------------------------------------------------
  95. Lindsey Smith                                            Symantec Corp.
  96. lsmith@symantec.com                                     Baton Rouge, LA
  97. From news@bigblue.oit.unc.edu Tue Feb  1 11:36:31 1994
  98. Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.06) with SMTP
  99.           id AA01081; Tue, 1 Feb 1994 11:36:31 -0500
  100. Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
  101.           id AA24795; Tue, 1 Feb 1994 11:17:36 -0500
  102. Received: from GATEWAY by bigblue with netnews
  103.     for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
  104. To: winsock@sunsite.unc.edu
  105. Date: Tue, 1 Feb 1994 08:47:00
  106. From: tgrel@kuhub.cc.ukans.edu (Tom Grelinger)
  107. Message-Id: <tgrel.53.0008C8CA@kuhub.cc.ukans.edu>
  108. Organization: University of Kansas Academic Computing
  109. Sender: ses
  110. References: <iniazi.4.00062ADF@vt.edu>, <2ihs4j$p08@news.csie.nctu.edu.tw>, <fengpc.82.2D4C7B08@leland.Stanford.EDU>
  111. Subject: Re: WINTALK v1.0.  Initiating a chat with wintalk.
  112.  
  113. In article <fengpc.82.2D4C7B08@leland.Stanford.EDU> fengpc@leland.Stanford.EDU (Feng, Pin-Cheng) writes:
  114. >Subject: Re: WINTALK v1.0.  Initiating a chat with wintalk.
  115. >From: fengpc@leland.Stanford.EDU (Feng, Pin-Cheng)
  116. >Date: Mon, 31 Jan 1994 03:29:12 GMT
  117.  
  118. >>Does WinTalk work file in Trumpet Beta5? I try it on 
  119. >>SuperTCP 3.00R1 , fine. But the 'can not get my host name' error
  120. >>raise! 
  121.  
  122. >Yes it's quite happy with Trumpet Beta5.
  123.  
  124. My earlier reports of bugs with it (crashing as soon as it loaded) might 
  125. related to the above problem.  But, I have found that if I load the program 
  126. AFTER loading another winsock program, it does not have a problem.
  127.  
  128. Tom.
  129. --------------------------------------------
  130. - Thomas P. Grelinger               -
  131. - Internet: tgrel@kuhub.cc.ukans.edu       -
  132. -           s3c100rr@cs.ukans.edu          -
  133. -        2fywposh@stat1.cc.ukans.edu    -
  134. - Fidonet: 1:299/4, 1:280/9           -
  135. --------------------------------------------
  136. From news@bigblue.oit.unc.edu Tue Feb  1 15:52:38 1994
  137. Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.06) with SMTP
  138.           id AA05635; Tue, 1 Feb 1994 12:06:32 -0500
  139. Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
  140.           id AA17271; Tue, 1 Feb 1994 11:37:14 -0500
  141. Received: from GATEWAY by bigblue with netnews
  142.     for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
  143. To: winsock@sunsite.unc.edu
  144. Date: Tue, 1 Feb 1994 15:52:38 GMT
  145. From: billw@coe.unomaha.edu (Bill Wilson)
  146. Message-Id: <billw.49.2D4E7AC6@coe.unomaha.edu>
  147. Organization: College of Education
  148. Sender: ses
  149. Subject: Where is WinTalk? Bsdchat?
  150.  
  151. I was interested in trying to find wintalk. Where can I find it?
  152.  
  153. Also, does anyone know where bsdchat.exe is located?
  154.  
  155. Thanks.
  156.  
  157.  
  158.  
  159.      +---------------------------------------+
  160.      | Bill Wilson                           |
  161.      | Technology Coordinator                |
  162.      | University of Nebraska at Omaha       |
  163.      | College of Education                  |
  164.      |                                       |
  165.      | Phone: (402) 554-3483                 |
  166.      | Fax:   (402) 554-2879                 |
  167.      |                                       |
  168.      | Email: billw@coe.unomaha.edu          |
  169.      +---------------------------------------+
  170.  
  171.